Allow SLE Micro system to access free SLES repositories #1247
Conversation
A SLE Micro system must have access to all free SLES repositories This Fixes bsc#1230419
|
You are defining, based on the product identifier of the registered base product, to infer which other products / repositories the system can use. That works, but is a lot of manual setup. Maybe there is an automatic way to find out that information, in the way how SCC is doing this: We have a manual config to build that connection for test subscriptions: https://github.com/SUSE/happy-customer/blob/master/glue/config/multi_product_classes.yml Just an idea, maybe this is a less manual, and more aligned with SCC way how to define access permission. |
@digitaltom It is a good idea, however, when I tested that, the subscription identifier in the activated products for the stand-alone SLE Micro (not SUMA) system was |
| @@ -12,7 +12,13 @@ def activate | |||
| end | |||
|
|
|||
| def show | |||
| if @system.products.include? @product | |||
| if @product.identifier.casecmp('sles').zero? | |||
There was a problem hiding this comment.
Is there no positive test here we can do? It feels inefficient to say "if it's not sles maybe it's sle-micro".
Description
A SLE Micro system must have access to all free SLES repositories
This Fixes bsc#1230419
How to test
On a SLE Micro PAYG instance, configured according to the documentation to use Podman,
running
zypper lrinside the container should showSLESrepositoriesOn a SUMA 5.0 instance, activating SUMA 4.3 should also activate the recommended SLES repositories
Change Type
Please select the correct option.
Checklist
Please check off each item if the requirement is met.
MANUAL.mdfile with any changes to the user experience.package/obs/rmt-server.changes.Review
Please check out our review guidelines
and get in touch with the author to get a shared understanding of the change.